Course Name | Database Systems |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
CE 223 | Spring | 3 | 2 | 4 | 7 |
Prerequisites | None | |||||
Course Language | English | |||||
Course Type | Required | |||||
Course Level | First Cycle | |||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | Problem SolvingApplication: Experiment / Laboratory / WorkshopLecture / Presentation | |||||
Course Coordinator | ||||||
Course Lecturer(s) | ||||||
Assistant(s) |
Course Objectives | The goal of this course is to give basic knowledge of database systems to a student who intends to be a computer or software engineer. It provides a comprehensive introduction to relational data model and entityrelationship data model as a design tool. Functional and multivalued dependencies in the context of normalization process are described in detail for designing relational database schema. SQL database language and system aspects of SQL such as transaction management, indexing, constraints, triggers and authorization are studied in detail together with laboratory practices illustrating different ways of database programming. |
Learning Outcomes | The students who succeeded in this course;
|
Course Description | Topics related to both database design and database programming are covered. |
Related Sustainable Development Goals |
| Core Courses | X |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction to Database Systems, Relational Data Model, Semi Structured Data Model | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 1, Ch. 2.1, 2.2, 2.3, Ch. 11.1, 11.2, 11.3) |
2 | Entity-Relationship Data Model | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 4.1, 4.2, 4.3, 4.4, 4.5, 4.6) |
3 | Introduction to Relational Databases, Functional Dependencies | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 2.4, 3.1, 3.2, 3.3, 3.4, 3.5) |
4 | Design of Relational Databases, Multivalued Dependencies | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 3.6, 3.7) |
5 | Functional Dependencies and Multivalued Dependencies Revisited | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 2.4, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7) |
6 | Introduction to SQL (Part I) | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 6.1, 6.2, 6.3, 6.4.1, 6.4.2) |
7 | Introduction to SQL (Part II) | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 5.2, 6.4, 6.5) |
8 | Midterm | |
9 | Constraints and Triggers | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 7) |
10 | SQL Programming: Embedded SQL, PSM (PL/SQL) | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 9.3, 9.4) |
11 | SQL Programming: CLI, JDBC, PHP/PEAR | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 9.1, 9.2, 9.5, 9.6, 9.7) |
12 | Transactions, Views, Indexes | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 6.6, 8.1, 8.2, 8.3, 8.4, 8.5) |
13 | SQL Authorization | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 10.1) |
14 | Logical Query Languages (Datalog) and SQL Recursion | J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008 (Ch. 5.3, 5.4, 10.2) |
15 | Review of the Semester | |
16 | Final Exam |
Course Notes/Textbooks | Textbook "J. D. Ullman, J. Widom, A First Course In Database Systems, 3/e, PrenticeHall, 2008" and course slides (Book’s URL: http://wwwdb.stanford.edu/~ullman/fcdb.html) |
Suggested Readings/Materials | Reference Book: Silberschatz et. al., Database System Concepts, 4th ed., McGrawHill, 2002. |
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | 1 | 15 |
Field Work | ||
Quizzes / Studio Critiques | 1 | 15 |
Portfolio | ||
Homework / Assignments | 1 | |
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 30 |
Final Exam | 1 | 40 |
Total |
Weighting of Semester Activities on the Final Grade | 4 | 60 |
Weighting of End-of-Semester Activities on the Final Grade | 1 | 40 |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | 2 | |
Study Hours Out of Class | 14 | 3 | 42 |
Field Work | |||
Quizzes / Studio Critiques | 1 | 15 | |
Portfolio | |||
Homework / Assignments | 12 | 2 | |
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 21 | |
Final Exams | 1 | 28 | |
Total | 210 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | To have adequate knowledge in Mathematics, Science and Computer Engineering; to be able to use theoretical and applied information in these areas on complex engineering problems. | X | ||||
2 | To be able to identify, define, formulate, and solve complex Computer Engineering problems; to be able to select and apply proper analysis and modeling methods for this purpose. | X | ||||
3 | To be able to design a complex system, process, device or product under realistic constraints and conditions, in such a way as to meet the requirements; to be able to apply modern design methods for this purpose. | X | ||||
4 | To be able to devise, select, and use modern techniques and tools needed for analysis and solution of complex problems in Computer Engineering applications; to be able to use information technologies effectively. | X | ||||
5 | To be able to design and conduct experiments, gather data, analyze and interpret results for investigating complex engineering problems or Computer Engineering research topics. | X | ||||
6 | To be able to work efficiently in Computer Engineering disciplinary and multi-disciplinary teams; to be able to work individually. | |||||
7 | To be able to communicate effectively in Turkish, both orally and in writing; to be able to author and comprehend written reports, to be able to prepare design and implementation reports, to present effectively, to be able to give and receive clear and comprehensible instructions. | |||||
8 | To have knowledge about global and social impact of Computer Engineering practices on health, environment, and safety; to have knowledge about contemporary issues as they pertain to engineering; to be aware of the legal ramifications of Computer Engineering solutions. | |||||
9 | To be aware of ethical behavior, professional and ethical responsibility; to have knowledge about standards utilized in engineering applications. | |||||
10 | To have knowledge about industrial practices such as project management, risk management, and change management; to have awareness of entrepreneurship and innovation; to have knowledge about sustainable development. | |||||
11 | To be able to collect data in the area of Computer Engineering, and to be able to communicate with colleagues in a foreign language. ("European Language Portfolio Global Scale", Level B1) | |||||
12 | To be able to speak a second foreign language at a medium level of fluency efficiently. | |||||
13 | To recognize the need for lifelong learning; to be able to access information, to be able to stay current with developments in science and technology; to be able to relate the knowledge accumulated throughout the human history to Computer Engineering. |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest